Skip to content

fix(release): skip unsupported windows/arm build target - #37

Merged
PF9-pushkar merged 1 commit into
mainfrom
fix/goreleaser-windows-arm
Aug 7, 2026
Merged

fix(release): skip unsupported windows/arm build target#37
PF9-pushkar merged 1 commit into
mainfrom
fix/goreleaser-windows-arm

Conversation

@PF9-pushkar

Copy link
Copy Markdown
Collaborator

A local GoReleaser snapshot dry-run (RELEASING.md Phase 1, Step 4) failed:

⨯ release failed: build failed: failed to build for windows_arm_6:
  go: unsupported GOOS/GOARCH pair windows/arm

The build matrix (goos includes windows, goarch includes arm) produces windows/arm, which Go has no target for. CI's goreleaser check only validates config syntax, not builds — so this would have surfaced only on the first real tagged release, failing the release workflow after a tag push.

Fix: add windows/arm to the ignore list (alongside the existing darwin/386).

Verified with goreleaser release --snapshot --clean --skip=sign: clean build producing 13 platform zips (darwin amd64/arm64, freebsd 386/amd64/arm/arm64, linux 386/amd64/arm/arm64, windows 386/amd64/arm64) + SHA256SUMS + the protocol-6 manifest.json.

A local goreleaser snapshot build fails with "unsupported GOOS/GOARCH pair
windows/arm" — Go has no 32-bit ARM Windows target, but the build matrix
(goos includes windows, goarch includes arm) produced that combination. CI's
goreleaser check only validates config syntax, so this would have surfaced only
on the first real tagged release. Add windows/arm to the ignore list. Verified
with a snapshot build: 13 platform zips + SHA256SUMS + manifest.json.
@PF9-pushkar
PF9-pushkar merged commit 211374e into main Aug 7, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant